Skip to content

Conversation

@He-Pin
Copy link
Contributor

@He-Pin He-Pin commented Nov 6, 2025

Motivation and Context

Control how the client session ID is generated.

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Signed-off-by: He-Pin <hepin1989@gmail.com>
@Kehrlann
Copy link
Contributor

Kehrlann commented Nov 18, 2025

@He-Pin What's the use-case for this? What are you trying to accomplish?

@Kehrlann Kehrlann self-assigned this Nov 18, 2025
@He-Pin
Copy link
Contributor Author

He-Pin commented Nov 18, 2025

we are building an mcp hub, we are encoding informations inside the sessionId, otherwise we have to change it with a varhandle

@Kehrlann
Copy link
Contributor

What kind of info are you encoding?

This PR is modifying the request ID generation scheme within a given session, not the session ID itself. As I understand it, the request ID is for request-response reconciliation within a given session. So I guess you need client-related info in the request ID ... is there are reason to use the request ID rather than meta ?

@He-Pin
Copy link
Contributor Author

He-Pin commented Nov 18, 2025

Oh, I finally recovered my memory, I was think that's the session id, will close and resubmit a new pr. thanks

@He-Pin He-Pin closed this Nov 18, 2025
@He-Pin He-Pin deleted the generateRequestId branch November 18, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants